Description

Add e2e tests for the dev command lifecycle: create a project, start the dev server, invoke it, and verify responses.

Three tests covering the core dev workflow:

• Server startup: dev --logs starts server and accepts connections
• Invoke: dev "prompt" sends a prompt to the running server and gets a non-empty response
• Stream invoke: dev "prompt" --stream streams a response from the running server (or at least returns a response).

Note: INIT_CWD must be stripped from the spawned process environment, otherwise agentcore resolves the working directory to the test runner root instead of the project directory. spawnAndCollect already handles this, but the raw spawn used for the background server process needed the same treatment. Therefore we moved this into a shared utility for future cases.

docs: https://docs.npmjs.com/cli/v10/commands/npm-run-script

Tests run in ~20s (no AWS deploy needed — dev server runs locally) and use Strands/Bedrock with a Python agent.

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• I ran npm run test:unit and npm run test:integ
• I ran npm run typecheck
• I ran npm run lint
• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

All 3 tests pass locally against dev account.

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.